Method and system for identifying a component within a vehicle for maintenance

ABSTRACT

Embodiments of the present invention provide method and system for determining whether to effect maintenance of a vehicle component. In one embodiment, the method includes transmitting an RFID read signal to an RFID device associated with at least one component of a vehicle and receiving at least one RFID response signal from the RFID device. The at least one RFID response signal includes an identifier associated with the at least one component and a sensed value of a parameter associated with the at least one component. Then, by processing the sensed value, it can be determined whether to effect maintenance of the at least one component. In some embodiments, the sensed value is generated by a sensor coupled to the RFID device. In other embodiments, the sensor is located adjacent to an expected location of the at least one component. In yet other embodiments, a location indication is utilized to determine whether to effect maintenance of the at least one component.

FIELD OF THE INVENTION

This invention relates generally to identifying components within avehicle and more specifically to a method and system for identifying acomponent within a vehicle for maintenance.

BACKGROUND OF THE INVENTION

Rotatable objects such as wheel assembly components are often a failurepoint on wheeled vehicles, such as rail cars, automobiles, trucks etc.In some vehicles, such as rail cars, wheel assemblies are attached tothe vehicles via a bearing assembly component which extends from theface of the wheel. The vehicle rests on the bearing assembly which,along with the wheel assembly, supports the weight of the vehicle.Hence, much stress is placed on the wheel assembly and its componentsthrough this supporting function, and further stress is placed on thebearing assembly, and the various other components of the wheelassembly, via acceleration forces placed on the vehicle. Wheelassemblies are thus prone to seizing up, and may be a key failure pointon the vehicles.

Maintenance of the wheel assembly components is thus an important aspectof vehicle maintenance, and rail car maintenance specifically. Further,an understanding of the history of each wheel assembly component can bea key factor in making decisions about the maintenance schedule of thewheel assembly component and the wheel assembly itself. For example, awheel assembly component that has been in use for a long period of timemay benefit from preventative maintenance. However, this may only becost effective if it is done at an appropriate time, which requires arecord to be maintained of how long the wheel assembly has been in use.Further, wheel assembly components which have been in higher than normalstress situations may also benefit from preventative maintenance.Examples of higher than normal stress situations might be an accident,undue vibration due to poorly maintained areas of track, or travelthrough harsh terrains and/or weather conditions. Another indicator thata wheel assembly component would benefit from maintenance is thetemperature of a wheel assembly component that is in use or has recentlybeen in use: wheel assembly components that contain worn, moving partstend to heat up due to friction. An example of such a wheel assemblycomponent is again a bearing assembly.

The history of the maintenance schedule of the wheel assembly componentmay also be a key factor in determining future maintenance schedules ofthe wheel assembly component. For example, a common procedure duringmaintenance is to machine the moving parts of a bearing assembly toreduce frictional stress. However, this can be an expensive procedure,in that the wheel assembly must be disassembled, as must the bearingassembly, and the machining must be precise. Further, a bearing assemblymay accept only a limited number of these procedures throughout itslife, as material is removed from the bearing assembly during themachining process. Hence, machining a bearing assembly is a procedurewhich might be performed only from time to time, and not as a routineprocedure.

Hence, it is desirable to track the history of wheel assemblycomponents, including both the in-use history of the wheel assemblycomponent, as well as the maintenance history of the wheel assemblycomponent, for making decisions about future maintenance schedules.Understanding the history of the wheel assembly component may also bebeneficial in warranty tracking and management. One solution fortracking the maintenance history of a wheel assembly component has beento physically mark the wheel assembly components with an alpha-numericidentifier, such as an identification number, and then manually trackthe status of the wheel assembly component by recording events in thehistory of the wheel assembly component against the identificationnumber. However, this solution relies on a maintenance workerremembering to record the identification number, and to cross referenceevents. Further, this does not address the problem of tracking thein-use history of the wheel assembly component. Returning again to theexample of the bearing assembly, in situations where many rail cars aremoving in and out of a maintenance yard, it is not practical to stopeach train and check the number of each bearing assembly on each railcar.

SUMMARY OF THE INVENTION

According to a first broad aspect, the present invention seeks toprovide a method of determining whether to effect maintenance of avehicle component. The method comprises transmitting an RFID read signalto an RFID device associated with at least one component of a vehicleand receiving at least one RFID response signal from the RFID device.The at least one RFID response signal comprises an identifier associatedwith the at least one component and a sensed value of a parameterassociated with the at least one component. The method further comprisesprocessing the sensed value to determine whether to effect maintenanceof the at least one component.

According to a second broad aspect, the present invention seeks toprovide a system comprising an RFID device reader and a computingentity. The RFID device reader is configured to transmit an RFID readsignal to an RFID device associated with at least one component of avehicle and receive at least one RFID response signal from the RFIDdevice. The at least one RFID response signal comprises an identifierassociated with the at least one component and a sensed value of aparameter associated with the at least one component. The computingentity is configured to process the sensed value to determine whether toeffect maintenance of the at least one component.

According to a third broad aspect, the present invention seeks toprovide a method of determining whether to effect maintenance of avehicle component. The method comprises receiving a sensed value of aparameter associated with at least one component of a vehicle andidentifying the at least one component of the vehicle associated withthe sensed value by receiving an identifier from a tracking deviceconfigured to rotate with movement of the vehicle. The tracking deviceis coupled to the at least one component. The method further comprisesprocessing the sensed value to determine whether to effect maintenanceof the at least one component.

According to a fourth broad aspect, the present invention seeks toprovide a system comprising a tracking device, a tracking device readerand a computing entity. The tracking device is coupled to at least onecomponent of a vehicle and is configured to rotate with movement of thevehicle and to transmit an identifier. The tracking device reader isconfigured to receive a sensed value of a parameter associated with theat least one component and identify the at least one componentassociated with the sensed value by receiving the identifier of thetracking device. The computing entity is configured to process thesensed value to determine whether to effect maintenance of the at leastone component.

According to a fifth broad aspect, the present invention seeks toprovide a method of determining whether to effect maintenance of avehicle component. The method comprises transmitting an RFID read signalto an RFID device associated with at least one component of a vehicleand receiving at least one RFID response signal from the RFID device.The at least one RFID response signal comprises an identifier associatedwith the at least one component and a location indication associatedwith the at least one component. The method further comprises processingthe location indication to determine whether to effect maintenance ofthe at least one component.

According to a sixth broad aspect, the present invention seeks toprovide a system comprising an RFID device reader and a computingentity. The RFID device reader is configured to transmit an RFID readsignal to an RFID device associated with at least one component of avehicle and receive at least one RFID response signal from the RFIDdevice. The at least one RFID response signal comprises an identifierassociated with the at least one component and a location indicationassociated with the at least one component. The method further comprisesa computing entity configured to process the location indication todetermine whether to effect maintenance of the at least one component.

According to a seventh broad aspect, the present invention seeks toprovide a method of flagging a vehicle component for maintenance. Themethod comprises receiving an identifier from an RFID device associatedwith at least one component of a vehicle, determining whether to effectmaintenance of the at least one component and transmitting a maintenanceindication to the RFID device if it is determined to effect maintenanceof the at least one component.

These and other aspects and features of the present invention will nowbecome apparent to those of ordinary skill in the art upon review of thefollowing description of specific embodiments of the invention inconjunction with the accompanying drawings.

BRIEF DESCRIPTIONS OF THE DRAWINGS

Embodiments of the present invention are described with reference to thefollowing figures, in which:

FIG. 1 depicts a system for tracking a wheel assembly component,according to an embodiment of the present invention;

FIG. 2 depicts an exploded view of a wheel assembly, according to anembodiment of the present invention;

FIG. 3 depicts a system for tracking a wheel assembly component,according to an alternative embodiment of the present invention;

FIG. 4 depicts a block diagram of a tracking device, according to anembodiment of the present invention;

FIG. 5 depicts a block diagram of a tracking device reader, according toan embodiment of the present invention;

FIG. 6 depicts a block diagram of a data input device, according to anembodiment of the present invention;

FIG. 7 depicts a data input device, according to an alternativeembodiment of the present invention;

FIG. 8 depicts a system for tracking a wheel assembly component,according to an embodiment of the present invention;

FIG. 9 depicts a block diagram of a computing entity, according to anembodiment of the present invention;

FIG. 10 depicts a table of a database, according to an embodiment of thepresent invention;

FIG. 11 depicts a table of a database, according to an embodiment of thepresent invention;

FIG. 12 depicts a system for tracking a wheel assembly component,according to an embodiment of the present invention;

FIG. 13 depicts a table of a database, according to an embodiment of thepresent invention;

FIG. 14 depicts a perspective of a bearing assembly and a trackingdevice, according to an embodiment of the present invention;

FIGS. 15A to 15D depict various views of a tracking device, according toan embodiment of the present invention;

FIG. 15E depicts a perspective view of detail of a tracking device,according to an embodiment of the present invention;

FIG. 16A depicts a perspective view of a bearing assembly and a trackingdevice, according to an embodiment of the present invention;

FIG. 16B depicts a side view of a bearing assembly and a trackingdevice, according to an embodiment of the present invention;

FIG. 17A depicts a perspective view of a tracking device secured to abearing assembly, according to an embodiment of the present invention;

FIG. 17B depicts a side view of a tracking device secured to a bearingassembly, according to an embodiment of the present invention;

FIG. 18A depicts a perspective view of a bearing assembly and a trackingdevice, according to an embodiment of the present invention;

FIG. 18B depicts a side view of a bearing assembly and a trackingdevice, according to an embodiment of the present invention;

FIG. 19 depicts a side view of a tracking device secured to a bearingassembly, according to an embodiment of the present invention;

FIG. 20 depicts a perspective view of a tracking device, according to analternative embodiment of the present invention;

FIG. 21 depicts a side view of a tracking device, according to analternative embodiment of the present invention;

FIG. 22 depicts a perspective view of a bearing assembly and a trackingdevice attachment portion, according to an embodiment of the presentinvention; and

FIG. 23 depicts a method of refurbishing a bearing assembly, accordingto an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 1 depicts a system for tracking a wheel assembly component,according to one embodiment of the present invention. A tracking device110, for storing data associated with a wheel assembly component of awheel assembly 120, is attached to a component of the wheel assembly120. In this embodiment, the tracking device 110 is attached to at leastone of a pair of bearing assemblies 160. A tracking device reader 130 isconfigured for contactless reading of data stored in the tracking device110. In this embodiment, the tracking device reader 130 is locatedadjacent to an expected location of the bearing assembly 160. However,in other embodiments, the tracking device reader 130 may not be locatedadjacent to an expected location of the tracking device 110, asdescribed below. The tracking device reader 130 is in communication witha computing entity 140, via a communication network 150, and is furtherconfigured to transmit data to the computing entity 140.

FIG. 2 depicts an exploded view of the wheel assembly 120 that showsvarious wheel assembly components of the wheel assembly 120. In thisexample, the wheel assembly components comprise an axle 210 joining apair of wheels 220. The wheel assembly components may further compriseapparatus to join the axle 210 to the wheels 220, as is known to one ofskill in the art. The wheel assembly components further compriseapparatus for supporting a vehicle frame (not shown) of a vehicle.Non-limiting examples of a vehicle include a railway vehicle, a truck, atrailer, a bus, an automobile, etc. In this example, the apparatus forsupporting a vehicle frame comprises the pair of bearing assemblies 160coupled to an outer face 225 (only one depicted) of each wheel 220. Eachbearing assembly 160 comprises a plurality of sub-components forcoupling the vehicle frame to the wheel 220, and includes moving partsconfigured to allow the wheel to rotate with respect to the frame. Othermechanisms for coupling a vehicle frame to the wheel assembly componentwill occur to those of skill in the art. The wheel assembly may furtherinclude a braking apparatus, various other bearing assemblies, shockabsorbers, tires (on road-based vehicles), and other mechanisms known toone of skill in the art.

While FIG. 1 depicts the tracking device 110 configured for attachmentto the bearing assembly 160, the tracking device 110 may be configuredfor attachment to another wheel assembly component. For example, FIG. 3depicts a system for tracking a wheel assembly component, according toan alternative embodiment of the present invention. The system depictedin FIG. 3 is substantially similar to the system depicted in FIG. 1,with like components represented by like numbers. In this embodiment,the tracking device 110 is configured for attachment to the axle 210,and the tracking device reader 110 is located adjacent to an expectedlocation of the axle 210. In yet other embodiments, the tracking device110 may be configured for attachment to another component of the wheelassembly 120. Non-limiting embodiments for attachment of the trackingdevice 110 to a component of the wheel assembly 120 are described below.

The tracking device 110 is generally configured to track the wheelassembly component to which it is attached. However, in an alternativeembodiment, the tracking device 110 may be configured to track the wheelassembly 120 as a whole, with the data stored in the tracking device 110associated with the wheel assembly as a whole. In yet other embodiments,the system may be configured to track a plurality of wheel assemblycomponents that make up the wheel assembly 120, with the data stored inthe tracking device 110 associated with the plurality of wheel assemblycomponents. In these embodiments, a subset of wheel assembly componentsmay travel together and share similar maintenance schedules.

In yet another embodiment, the system depicted in FIG. 1 or 3 mayfurther comprise a plurality of tracking devices 110, each attached to adifferent wheel assembly component. In one non-limiting example, thesystem depicted in FIG. 1 may comprise two tracking devices 110, oneattached to each of the pair of bearing assemblies 160. In theseembodiments, the tracking device reader 130, may be configured to readthe data stored on the plurality of tracking devices 110. In analternative embodiment, there may be a plurality of tracking devicereaders 130, each located at a position where the tracking device 110may be available for contactless reading of data stored in the trackingdevice 110, for example adjacent to an expected location of each wheelassembly component, each tracking device reader 130 being configured toread data stored at each tracking device 130, in a one-to-onerelationship. Alternatively, there may be fewer tracking device readers130 than tracking devices 110, and each tracking device reader 130 maybe configured to read data stored on two or more tracking devices 110.

In one non-limiting example, there may a tracking device 110 attached toeach of the pair of bearing assemblies 160, and a tracking device 110attached to each wheel 220. Further, there may be a pair of trackingdevice readers 130 located on either side of an expected location of thewheel assembly 120, one tracking device reader 130 configured to readall tracking devices 110 located on a first side of the wheel assembly120, and the other tracking device reader 130 configured to read alltracking devices 110 located on the second side of the wheel assembly120.

Data that may be stored in the tracking device 110 may include any dataassociated with the wheel assembly component to which it is attached,the wheel assembly 120 of which is part the wheel assembly component, ora plurality of wheel assembly components part of the wheel assembly 120.Examples of data that may be stored include, but are not limited to: anidentification number of at least one wheel assembly component and/orthe wheel assembly 120, the configuration of at least one wheel assemblycomponent and/or the wheel assembly 120, the history of at least onewheel assembly component and/or the wheel assembly 120, a warrantynumber of at least one wheel assembly component and/or the wheelassembly 120, the manufacturing date of at least one wheel assemblycomponent and/or the wheel assembly 120, a refurbishment date of atleast one wheel assembly component and/or the wheel assembly 120, or anycombination thereof.

In some embodiments, the tracking device 110 may comprise an electronictracking device. FIG. 4 depicts a block diagram of an embodiment of thetracking device 110, configured to electronically store and communicatedata associated with a wheel assembly component. Such a device mayinclude a memory portion 410, configured to store the data associatedwith the wheel assembly component, and a communication portion 420,configured to communicate with the tracking device reader 130. In someembodiments, the memory 410 is a read-only static memory, and the datastored in the memory 410 may be stored in the memory 410 at the time ofmanufacture, or via another one-time write only process. In thisembodiment, the communication portion 420 may be configured to transmitthe data stored in the memory 410. However, in other embodiments, thememory 410 may be a dynamic memory, and data stored in the memory 410may be updated. In this embodiment, the communication portion 420 may beconfigured to both transmit the data, and receive data to be stored inthe memory 410. Hence, in this embodiment, the communication portion 420may be configured to communicate with both the tracking device reader130, and a tracking device writer (not depicted). In some embodiments,the tracking device reader 130 and the tracking device writer may beseparate devices. In other embodiments, as described below, the trackingdevice reader 130 may further comprise a tracking device writer.

In some embodiments, the tracking device 110 may be a passive trackingdevice. In such embodiments, and again with reference to FIG. 1, thetracking device reader 130 may be configured to transmit a request 132to the tracking device 110. In response, the data stored in the trackingdevice 110 is transferred from the tracking device 110 to the at leastone tracking device reader 130, via a data transmission 134.

In these embodiments, the tracking device 110 may comprise a passiveradio frequency identification (RFID) device, known to one of skill inthe art. Also, the communication portion 420 comprises an antenna, theantenna being configured to both receive data for storage in the memory410, and further configured to transmit data which is stored in thememory. In this embodiment, the request 132 comprises an RF signaltransmitted by the tracking device reader 130. In these embodiments, thetracking device reader 130 comprises an RFID reader. As known by thoseof skill in the art, passive RFID devices are powered inductively by theRF signal received from the RFID reader. Hence, the request 132 isreceived by the antenna, and is used by the passive RFID device toprovide power for retrieving the data from the memory 410, and the datatransmission 134.

In other embodiments, the tracking device 110 may be a semi-passivetracking device. Semi-passive tracking devices are similar to passivetracking devices as described above, however semi-passive trackingdevices may include a power source (e.g. a battery) to power the datatransmission 134. In one non-limiting example, the tracking device 110may comprise a semi-passive RFID device, known to one of skill in theart. Semi-passive RFID devices are substantially similar to passive RFIDdevices, however semi-passive RFID device may include a battery to powerthe data transmission 134.

In other embodiments, the tracking device 110 may comprise an activetracking device. In these embodiments, the tracking device 110 may alsocomprise a power source 440, such as a battery, to power the memory 410and the communication portion 420. Alternatively, the power source 440may comprise an electrical connection to an on-board vehicle powersource. Hence, while in some embodiments the data transmission 134 mayoccur in response to receiving the request 132, in alternativeembodiments, the data transmission 134 may occur in the absence of arequest 132. In one embodiment, the data transmission 134 may occur on aperiodic basis. Alternatively, the tracking device 110 may furthercomprise a proximity detector configured to detect the presence of thetracking device reader 130. The proximity detector is further configuredto generate a trigger when the at least one tracking device reader 130is detected. The trigger may be received by the communication portion420 which, in response, triggers the data transmission 134.

In these embodiments, the tracking device 110 may comprise an activeradio frequency identification (RFID) device, known to one of skill inthe art, which functions in substantially the same manner as passiveRFID devices described above. However, the power source 440 maygenerally comprise a battery used to power the active RFID device,including the data transmission 134. In this manner, the broadcast rangeof the active RFID device may be increased, relative to the passive RFIDdevice.

In other embodiments, the tracking device 110 may comprise a semi-activetracking device. Semi-active tracking devices are similar to activetracking devices as described above, however semi-active trackingdevices may not turn on until triggered by an external or an internalsensor (see below).

In an alternative embodiment of active electronic tracking device, thetracking device 110 may further comprise a sensor 430 for activelysensing data associated with the environment of the wheel assemblycomponent of the wheel assembly 120, and for transmitting the senseddata to the memory 410 for storage. The power source 440 is furtherconfigured to power the sensor 430 in these embodiments. In someembodiments, the tracking device 110 may hence also comprise a clock ortimer (not depicted), such that the time that the data was collected bythe sensor 430 may also be transmitted to the memory 410 for storage. Inalternative embodiments, the tracking device 110 may be in communicationwith an external sensor (not depicted) mounted on the wheel assemblycomponent, or another component of the wheel assembly 120, the externalsensor being configured to collect data associated with the environmentof the area where the external sensor is mounted, and being furtherconfigured to transmit the data to the tracking device 110 for storagein memory 410. In embodiments where the tracking device 110 comprises asemi-active tracking device and the semi-active tracking device includesthe sensor 430, or the semi-active tracking device is in communicationwith an external sensor, the semi-active tracking device may be turnedon by an event occurring at the sensor 430 or the external sensor,described below.

In another non-limiting embodiment for sensing data associated with theenvironment of the wheel assembly component of the wheel assembly 120,as depicted in FIG. 12, an external sensor apparatus 1210 may be locatedadjacent to an expected location of the wheel assembly component,generally in the vicinity of the tracking device reader 130. The systemdepicted in FIG. 12 is substantially similar to the system depicted inFIG. 1, with like components represented by like numbers. The sensorapparatus 1210 is configured for contactless measurement of dataassociated with the environment of the wheel assembly component. Thesensor apparatus 1210 is further configured to transmit the measureddata to the computing entity 140 via the communication network 150. Inan alternative embodiment, the sensor apparatus 1210 is in communicationwith the tracking device reader 130 which, in these embodiments, isconfigured to receive the measured data from the sensor apparatus 1210and transmit the measured data to the computing entity 140. In theseembodiments, the sensor apparatus 1210 may be configured for wirelesscommunication with the tracking device reader 130. In yet othernon-limiting embodiments, the tracking device reader 130 is configuredto receive the measured data from the sensor apparatus 1210 and transmitthe measured data to the tracking device 110, for storage in the memory410 of the tracking device, as described below with reference to FIG. 5.In these embodiments, the measured data may be later retrieved from thetracking device 110 by the tracking device reader 130, or by anothertracking device reader.

In some of these embodiments, the sensor apparatus 1210 is incommunication with the tracking device reader 130 via the communicationnetwork 150, however in other embodiments the sensor apparatus 1210 maybe in direct wired or wireless communication with the tracking devicereader 130. In one non-limiting example, the sensor apparatus 1210comprises an infrared temperature sensing apparatus configured to sensethe temperature of the bearing assembly 160. The temperature of thebearing assembly is measured by the sensor apparatus 1210 andtransmitted to the computing entity 140. In general, the measurement ofthe temperature of the bearing assembly 160 will be associated with thetracking device reader 130 simultaneously reading the data from thetracking device 110 attached to the bearing assembly. In somenon-limiting embodiments, the computing entity 140 is configured toassociate the measured data with the data received from the trackingdevice reader 130 by the time which the measured temperature and thedata from the tracking device reader 130 arrive at the computing entity140. In other non-limiting embodiments, the sensor apparatus 1210 mayfurther store an identifier associated with the location of the reader130, and the identifier associated with the location of the reader 130is further transmitted to the computing entity 140 with the measureddata. In these embodiments, the computing entity 140 is configured toassociate the measured data with the data received from the trackingdevice reader 130 using the identifier associated with the location ofthe reader 130 and an identifier received from the reader 130, describedbelow.

Returning now to FIG. 4, in a non-limiting example, the at least onesensor 430 may comprise at least one of a temperature sensor, vibrationsensor, a pressure sensor, a torque sensor, a tamper proof sensor, ashock sensor, or a gyroscopic sensor. In some embodiments, the memory410 may be configured to store data collected at the sensor 430 on aperiodic basis. For example, in the embodiment where the sensor 430comprises a temperature sensor, the memory 410 may be configured tostore the temperature at the tracking device 110 periodically. However,in other embodiments, the memory 410 may be configured to store datacollected at the sensor 430 only upon the occurrence of a data valuereaching a pre-defined threshold.

For example, in the embodiment where the sensor 430 comprises atemperature sensor, the memory 410 may be configured to store thetemperature at the tracking device 110 when the temperature rises abovea first threshold temperature, or falls below a second thresholdtemperature. In other embodiments, the memory 410 may be configured tostore the number of occurrences of the temperature rising above a firstthreshold temperature, or falling below a second threshold temperature.In yet other embodiments, the memory 410 may be configured to store thelength of time that the temperature was above a first thresholdtemperature, or below a second threshold temperature. In embodimentswhere the tracking device 110 is attached to a bearing assembly 160 on awheel assembly 120 that is mounted on a railcar, if the temperature ofthe bearing assembly 160 rises above the first threshold temperature,this may indicate an unacceptable level of friction in the bearingassembly 160, and that the bearing assembly 160 is due for maintenance.

In another example, in the embodiment where the sensor 430 comprises avibration sensor, the memory 410 may be configured to store thevibration at the tracking device 110 when the vibration level risesabove a threshold vibration. In other embodiments, the memory 410 may beconfigured to store the number of occurrences of the vibration risingabove a threshold vibration. In yet other embodiments, the memory 410may be configured to store the length of time that the vibration wasabove a threshold vibration. The vibration level rising above thethreshold may indicate that the wheel assembly component to which thetracking device 110 is attached has undergone stress and may be due fora maintenance procedure.

In another example, in the embodiment where the sensor 430 comprises ashock sensor, the memory 410 may be configured to store a shock event atthe tracking device 110. In one embodiment, a shock event may comprise asudden change in acceleration of the tracking device 110. A shock eventrecorded at the tracking device 110 may indicate that the wheel assemblycomponent to which it is attached has undergone stress and may be duefor a maintenance procedure.

In another example, in the embodiment where the sensor 430 comprises agyroscopic sensor, the memory 410 may be configured to store changes inthe orientation of the tracking device 110. In other embodiments, thememory 410 may be configured to store the number of occurrences of theorientation changing. In yet other embodiments, the memory 410 may beconfigured to store the length of time that orientation changed. In oneembodiment, a change in the orientation may comprise a change in theupright position of the tracking device 110, and may indicate that thewheel assembly component to which it is attached has also changed itsupright position, as may be the case in train derailment, for example.Changes in the orientation of the tracking device 110 may hence indicatethat the wheel assembly component to which it is attached has undergonestress and may be due for a maintenance procedure.

In another example, in the embodiment where the sensor 430 comprises apressure sensor, the memory 410 may be configured to store the pressureat the sensor 430 when the pressure level rises above a first thresholdpressure, or falls below a second threshold pressure. In otherembodiments, the memory 410 may be configured to store the number ofoccurrences of the pressure rising above a first threshold pressure, orfalling below a second threshold pressure. In yet other embodiments, thememory 410 may be configured to store the length of time that thepressure was above a first threshold pressure, or below a secondthreshold pressure. In this embodiment, the sensor 430 may be incommunication with a wheel assembly component where changes in pressureare an indicator of maintenance requirements, for example a hydraulicbraking mechanism. Losses in pressure, or very high pressures, mayindicate a problem with the braking mechanism, and hence that thebraking mechanism may be due for a maintenance procedure.

In another example, in the embodiment where the sensor 430 comprises atorque sensor, the memory 410 may be configured to store the torque atthe sensor 430 when the torque level rises above a first torque, orfalls below a second torque. In other embodiments, the memory 410 may beconfigured to store the number of occurrences of the torque rising abovea first threshold torque, or falling below a second threshold torque. Inyet other embodiments, the memory 410 may be configured to store thelength of time that the torque was above a first threshold torque, orbelow a second threshold torque. In this embodiment the sensor 430 maybe in communication with a wheel assembly component where changes intorque are an indicator of maintenance requirements, for example a wheel220, or an axle 210. Unexplained changes in torque may indicate aproblem with the wheel assembly component, and hence that the wheelassembly component may be due for a maintenance procedure.

In another example, in the embodiment where the sensor 430 comprises atamper proof sensor, the memory 410 may be configured to storeoccurrences of tampering with the tracking device 110 and/or the wheelassembly component to which it is attached. Tampering with the trackingdevice 110, or the wheel assembly component to which it is attached, mayindicate that the wheel assembly component may be due for a maintenanceprocedure.

Other embodiments of sensors and sensor data may occur to those of skillin the art and are within the scope of the present invention.

While the communication portion 420 has been described above withreference to RFID device, in another non-limiting example, thecommunication portion 420 may comprise a Bluetooth wirelesscommunication device. A Bluetooth wireless communication devicecomprises a wireless communication device which communicates with otherBluetooth wireless communication devices, according to a Bluetoothstandard. One non-limiting example of a Bluetooth standard comprisesBluetooth 2.0, as defined by the Bluetooth Special Interest Group (SIG)at www.bluetooth.org. In these embodiments, the tracking device reader130 may also comprise a Bluetooth wireless communication device.

In another non-limiting example, the communication portion 420 maycomprise a Zigbee wireless communication device. A Zigbee wirelesscommunication device comprises a wireless communication device whichcommunicates with other Zigbee wireless communication devices, accordingto a Zigbee standard. One non-limiting example of a Zigbee standardcomprises Zigbee 1.1, as defined by the Zigbee Alliance atwww.zigbee.org. In these embodiments, the tracking device reader 130 mayalso comprise a Zigbee wireless communication device.

Returning now to FIG. 1, in other non-limiting embodiments, the trackingdevice 110 may comprise an optical tracking device configured tooptically store data associated with a wheel assembly component. In someembodiments, the tracking device 110 may comprise an opticalrepresentation of data associated with the wheel assembly component towhich it is attached. In one non-limiting example, the opticalrepresentation may comprise at least one colour uniquely associated withthe wheel assembly component. In other embodiments the tracking device110 may comprise a graphical representation of data associated with thewheel assembly component to which it is attached. In these embodiments,the optical tracking device 110 may comprise a barcode, known to one ofskill in the art. In these embodiments, the barcode may be configuredfor reading by the tracking device reader 130 when the wheel assembly120 is stationary. In other embodiments, the barcode may be configuredfor reading by the tracking device reader 130 while the wheel assembly120 is in motion. In one embodiment, the barcode is configured to beattached to a rotatable wheel assembly component of the wheel assembly120, and further configured to be read by the tracking device reader130, when the wheel assembly component, and hence the tracking device110, is rotating. In one non-limiting example, the barcode is auniversal product code, though other barcode formats are within thescope of these embodiments of the present invention.

A further example of an optical tracking device 110 is an alpha-numericcode. In one embodiment, the alpha-numeric code comprises anidentification number for the wheel assembly component to which thetracking device 110 is attached.

Embodiments of the tracking device reader 130 for reading data fromoptical embodiments of the tracking device 1110 are discussed below.

FIG. 5 depicts a non-limiting embodiment of the tracking device reader130. The tracking device reader 130 is configured to receive data fromthe tracking device 110, and is further configured to transmit thereceived data to the computing entity 140. In general the technologyused in the tracking device reader 130 will be complementary to thetechnology used in the tracking device 110. For example, if the trackingdevice 110 comprises an electronic tracking device, then the trackingdevice reader 130 comprises an electronic tracking device reader. In thenon-limiting example discussed above, if the tracking device 110comprises an RFID device, the tracking device reader 130 comprises anRFID device reader. In another non-limiting example, if the trackingdevice 110 comprises a Bluetooth device, the tracking device reader 130comprises a Bluetooth device reader. However, in another example, if thetracking device 110 comprises an optical tracking device 110, then thetracking device reader 130 comprises an optical tracking device reader130. In a non-limiting example where the tracking device 110 comprises abarcode, the tracking device reader 130 comprises a barcode reader. Inanother non-limiting example, if the tracking device 110 comprises analpha-numeric code, the tracking device reader 130 comprises analpha-numeric code reader.

The tracking device reader 130 may include a receiving apparatus 510 forreceiving data from the tracking device 110, for example via the datatransmission 134. In embodiments where the tracking device 110 comprisesan electronic tracking device, the receiving apparatus 510 is configuredto receive the data transmission 134. In one non-limiting example, ifthe data transmission 134 comprises an RF signal, than the receivingapparatus 510 may comprise an antenna. In embodiments where the trackingdevice 110 comprises an optical tracking device 110, the receivingapparatus 510 is configured to optically receive the data transmission134. In one non-limiting example, the data transmission 134 may comprisean optical image of a graphical representation of data associated withthe wheel assembly component. Hence, the receiving apparatus 510comprises apparatus for receiving the optical image. In one non-limitingembodiment, the receiving apparatus 510 may comprise a camera. Inanother non-limiting embodiment, the receiving apparatus 510 maycomprise a diode array. In these embodiments, the tracking device reader130 may require a clear line of sight to the tracking device 110, inorder to read the tracking device 110. Other embodiments of apparatusfor reading an optical image may occur to those of skill in the art andare within the scope of the present invention.

In some embodiments, the tracking device reader 130 may further comprisea transmission apparatus 520 for transmitting the request 132 to thetracking device 110. In embodiments where the device 110 is expecting arequest 132 prior to initiating the data transmission 134, thetransmission apparatus 520 is configured to initiate the informationtransmission by electronically transmitting the request 132. However, inembodiments where the tracking device 110 is actively transmitting thedata transmission 134, the transmission apparatus 520 may be optional.

In some embodiments, where the tracking device 110 comprises anelectronic tracking device, the transmission apparatus 520 is configuredto electronically transmit the request 132. In one non-limiting example,if the request 132 comprises an RF signal, than the transmissionapparatus 520 may comprise an antenna. In these embodiments, thereceiving apparatus 510 and the transmission apparatus 520 may share anantenna, as indicated in FIG. 5 by the dotted lines surrounding the twoelements. In embodiments where the tracking device 110 is a passive RFIDdevice, the transmission apparatus 520 is configured to transmit theenergy for the data transmission 134.

In some embodiments where the tracking device 110 comprises anelectronic tracking device, the tracking device reader 130 may belocated so as to read the tracking device 110 when the tracking device110 enters a zone where the request 132 is transmitted, and may thus bereceived by the tracking device 110. In some embodiments, the locationof the tracking device reader 130 may be adjacent to an expectedlocation of the tracking device.

In embodiments where the tracking device 110 comprises an opticaltracking device, the tracking device reader 130 may rely on ambientlight to read the graphical representation of the data. However, inother embodiments, the tracking device reader 130 may further comprisean illumination apparatus 525 to optically enhance the graphicalrepresentation of the data. Non-limiting examples of an illuminationapparatus 525 include a light source, such as a light bulb, at least onelight-emitting diode (LED) or a laser. In some embodiments, theillumination apparatus 525 may be always on. In other embodiments, theillumination apparatus 525 may be configured to turn on in response toan optional proximity detector (described below) detecting the proximityof a wheel assembly component.

In embodiments where the tracking device 110 comprises a barcode and thetracking device reader 130 comprises a barcode reader, and theillumination apparatus 525 comprises a laser, the illumination apparatus525 may further comprise apparatus to scan the laser over the barcode,as known to one of skill in the art.

In some embodiments, the transmission apparatus 520 may be furtherconfigured to receive a trigger from a user, such that upon receipt ofthe trigger, the request 132 is transmitted to the tracking device 110.In a non-limiting example, the tracking device reader 130 may be aportable tracking device reader configured to receive a datatransmission 134 only when triggered by a user. In one non-limitingexample, the user may trigger the request 132 after placing the trackingdevice reader 130 in the proximity of the tracking device 110.

In other embodiments, the transmission apparatus 520 may be configuredto transmit the request 132 periodically. In these embodiments, theperiodicity of the transmission of the request 132 is configured so thatthe tracking device 110 will receive at least one of the requests 132.In particular, in embodiments where the tracking device reader 130 is ina location where the tracking device 110 to be read will be attached toa wheel assembly component which is in motion, for example on a movingrailway car, the periodicity of the request 132 must be often enoughthat the tracking device 110 will receive at least one of the requests132.

In some embodiments, the transmission apparatus 520 may be furtherconfigured to transmit data to the tracking device 110, the transmitteddata to be stored in the memory 410 of the tracking device 110. In otherembodiments, the transmission apparatus 520 may be further configured totransmit commands to the tracking device 110.

In other embodiments, the tracking device reader 130 may furthercomprise a presence detector (not depicted) for detecting the presenceof the tracking device 110 and/or the wheel assembly component to whichit is attached, and/or a wheel assembly, and/or a vehicle which thewheel assembly may be supporting. In these embodiments, the request 132may be initiated only when a presence is detected. Alternatively,periodic transmission of the request 132 may be initiated when presenceis detected. The periodic transmission of the request 132 may occur fora defined period of time. Alternatively, the periodic transmission ofthe request 132 may cease when presence is no longer detected.

In general, the at least one tracking device reader 130 is locatedadjacent to an expected location of the wheel assembly component towhich the tracking device 110 is attached. Non-limiting examples of suchexpected locations include, but are not limited to, an inventory controlarea, a maintenance shed, a factory, a railroad track, or a highway.Further, the tracking device reader 130 is configured at the expectedlocation such that the tracking device reader 130 is able to read thedata stored at the tracking device 110. For example, in embodimentswhere the receiving apparatus 510 and/or the transmission apparatus 520each comprise an antenna, the configuration of the receiving antenna maybe optimized so that the data transmission 134 is transmitted towardsthe receiving antenna, and the configuration of the transmitting antennamay be optimized so that the request 132 is transmitted towards theexpected location of the tracking device 110. In embodiments where thereceiving apparatus 510 comprises a camera, the line of sight of camerato the expected location of an optical tracking device may be optimized.

In some embodiments, the transmission apparatus 520 and the receivingapparatus 510 may be further configured with respect to each other, andwith respect to an expected direction of travel of the wheel assemblycomponent. In a non-limiting example, the transmission apparatus 520 maybe located at a first location. The receiving apparatus 510 may belocated at a second location further down the expected direction oftravel from the first location. The tracking device 110 attached to awheel assembly component moving in the expected direction of travel thusencounters the transmission apparatus 520 prior to encountering thereceiving apparatus 510. Hence, the tracking device 110 receives therequest 132 from the transmission apparatus 520 at the first location,and transmits the data transmission 134 to the receiving apparatus 510when the tracking device 110 reaches the second location. In embodimentsthat comprise the sensor apparatus 1210 of FIG. 12 in communication withthe tracking device reader 130, the sensor apparatus 1210 may be locatedat the first location, and the tracking device 110 may be configured totransmit measured data received from the sensor apparatus 1210 to thetracking device 110 for storage, at the second location.

In some embodiments, the tracking device reader 130 may further comprisea memory module 540 configured to store data associated with the atleast one tracking device reader 130. In one non-limiting example, datastored in the memory module 540 may comprise at least one of a locationof the tracking device reader 130 and an identification number of thetracking device reader 130. Other examples of data stored in the memorymodule 540 may occur to a person of skill in the art and are within thescope of the present invention. The memory module 540 may be furtherconfigured to store data received from the tracking device 110 via thedata transmission 134.

The tracking device reader 130 further comprises a processing module530. The processing module 530 may be configured to consolidate datareceived from the tracking device 110, data stored in the memory module540, and data received from an optional data input device 145 of FIG. 1(discussed below). Alternatively, the processing module 530 may beconfigured to process data received from the tracking device 110. In anon-limiting example, the processing module 530 may be configured toprocess the format of the data contained in the data transmission 134.The processing module 530 may be further configured to effect ahandshaking process between the tracking device 110 and the trackingdevice reader 130. In one non-limiting example, where the trackingdevice 110 and the tracking device reader 130 comprise RFID devices, theprocessing module 530 may be further configured to effect a RFIDhandshaking process between the two devices. The processing module 530may be further configured to transmit data to the computing entity 140via the communication network 150. In embodiments where the trackingdevice 110 comprises an optical tracking device, the processing module530 may be configured to processes optical images of the tracking device110, to extract the data contained within them.

In some embodiments, the system depicted in FIG. 1 further comprises aplurality of tracking device readers 130, each located at a differentexpected location of the wheel assembly component. In some embodiments,the location of at least one tracking device reader 130 is fixed.However, in other embodiments, at least one tracking device reader 130may be a portable device, intended to be brought to the expectedlocation of the wheel assembly component by a user. In yet otherembodiments, there may be a plurality of tracking device readers 130,some with fixed locations, and others which are portable.

In some embodiments, the system depicted in FIG. 1 may further comprisean optional data input device 145, configured to receive from a userdata associated with the wheel assembly component. The data input device145 is further configured to transmit the data to the tracking devicereader 130. However, in other embodiments, the data input device 145 maybe in communication with the computing entity 140 via the communicationnetwork 150, and may be configured to transmit the data to the computingentity 140. Data which may be entered into the data input device 145 bya user may comprise notes on the history of the wheel assemblycomponent, including but not limited to the assembly and/or maintenanceof the wheel assembly component, and/or the commissioning of the wheelassembly component and/or the configuration of the wheel assemblycomponent.

As illustrated in FIG. 6, in some embodiments, the data input device 145may comprise a human-machine interface (HMI) 610 configured to allow auser to input the data to the data input device. In some embodiments,the HMI 510 may comprise a keyboard and a display device for allowing auser to view the input data, for example via a graphical user interface(GUI). In other embodiments, the HMI 510 may comprise a display deviceconfigured with a GUI, and a touchscreen apparatus.

The data input device 145 may further comprise a memory module 620 forstoring the data received from a user prior to transmission of the data.The data input device may further comprise a transmission apparatus 630for transmitting data received from the user to another component of thesystem depicted in FIG. 1.

In some embodiments, the data input device 145 may be a portable device.In other embodiments, the data input device 145 and the tracking devicereader 130 may be combined into a data input device 145a, as depicted inFIG. 7. In one non-limiting example, the data input device 145a mayincorporate all the functionality of the portable tracking device reader130 embodiment described previously, along with the user data inputfunctionality of the data input device 145.

FIG. 8 depicts a non-limiting example of how data may be collected withthe system depicted in FIG. 1 and consolidated for transmission to thecomputing entity 140. In this example, data D1 comprises a first set ofdata, associated with a wheel assembly component, and stored in thememory portion 410 of the tracking device 110 attached to the wheelassembly component. In one non-limiting embodiment, data D1 may comprisean identifier of the wheel assembly component to which the trackingdevice is attached. In embodiments where the tracking device 110comprises a sensor 430, the data D1 may further comprise sensor data.Data D2 comprises a second set of data, associated with a trackingdevice reader 130, and which may be further associated with the wheelassembly component, and stored in the memory module 540 of the trackingdevice reader 130. In one non-limiting embodiment data D2 may comprisean identifier of the tracking device reader 130. In one non-limitingexample, the identifier of the tracking device reader 130 may comprisean internet protocol (IP) address. Data D3 comprises a third set ofdata, associated with a wheel assembly component, and entered by a userinto the optional data input device 145. Data D3 is stored in the memorymodule 620 of the data input device 145. In one non-limiting embodiment,data D3 may comprise text entered into the data input device 145 by auser, the text further describing the history of the tracking device110. For example, in embodiments where the wheel assembly componentcomprises the bearing assembly 160, the tracking device 110 attached tothe bearing assembly 160 having recently undergone a maintenanceprocedure, a user may enter the text “Bearings Machined” into the datainput device 145.

In this non-limiting example, the tracking device reader 130 receivesdata D1 from the tracking device 110 via the data transmission 134, inthe manner described previously. Optionally, around the same time as thedata transmission 134 occurs, a user of the data input device 145 mayenter data D3 into the data input device 145, to enhance or clarify thedata D1. The processing module 530 of the tracking device reader 130receives data D1 and data D3, and may retrieve data D2 from the memorymodule 540 of the tracking device reader 130. The processing module 530may then process data D1, D2, and/or D3 for transmission to thecomputing entity 140. The processing may comprise formatting the dataD1, D2, and/or D3 into a format preferred by the computing entity 140.The processing may also comprise compressing data D1, D2, and/or D3 fortransmission to the computing entity 140. In some embodiments, data D1,D2 and/or D3 may be transmitted sequentially to the computing entity140. However, in other embodiments D1, D2, and/or D3 may be consolidatedinto a single data set for transmission to the computing entity 140. Inembodiments that comprise a sensor apparatus 1210 in communication withthe tracking device reader 130, the tracking device reader 130 may befurther configured to receive sensor data from the sensor apparatus1210, and further configured to process the sensor data in a mannersimilar to data D1, D2 and/or D3.

FIG. 9 depicts a non-limiting embodiment of the computing entity 140,configured for receiving data associated with the wheel assemblycomponent from the tracking device reader 130, and further configuredfor tracking the history of the wheel assembly component. The computingentity 140 comprises a data management module 910, for managing the datareceived from the tracking device reader 130. The computing entityfurther comprises a database 920 for storing the data received from thetracking device reader 130. In some embodiments, the computing entitymay also comprise a communication module 930 for communicating with aninventory management system. In some embodiments, the components of thecomputing entity 140 may be co-located and may comprise, for example, aserver or a personal computer. In other embodiments, the components ofthe computing entity may be distributed across several geographiclocations, and in communication via the communication network 150, oranother communication network.

The data management module 910 is configured to receive the datatransmitted from the tracking device reader 130, and is furtherconfigured to transmit the data to the database 920. The data managementmodule 910 may be further configured to filter the data. In someembodiments, the data received from the tracking device reader 130 maycomprise redundant data. For example, in some embodiments, the trackingdevice reader 130 may read the data from a tracking device 110 multipletimes. In these embodiments, the data management module 910 may beconfigured to delete the redundant data. The data management module 910may be further configured to aggregate data received from the trackingdevice reader 130. For example, returning to FIG. 8, in embodimentswhere D1, D2 and/or D3 are transmitted sequentially, the data managementmodule 910 may be configured to consolidate D1, D2 and/or D3. Further,in embodiments where the tracking device 130 transmits data receivedfrom a plurality of tracking devices 110, the data management module 910may be configured to aggregate the data from the plurality of trackingdevices 110 prior to transmitting the data to the database 920. The datamanagement module 910 may also be configured to format the data receivedfrom the tracking device reader 130 for storage in the database 920. Forexample, the database 920 may expect to receive the data parsed in acertain format which is different from the format in which it isreceived at the data management module 910. Hence, the data managementmodule 910 may be configured to parse the data for storage in thedatabase 920. In embodiments where the tracking device 110 comprises apassive or an active RFID device, the data management module maycomprise RFID middleware, as known to one of skill in the art.

In some embodiments, the data management module 910 may further includea timing device and may be configured to add the date and/or time thatthe data was received to the data, prior to transmitting the data to thedatabase 920.

As depicted in FIG. 10, database 920 may comprise at least one table1000 corresponding to at least one wheel assembly component. The table1000 may comprise a field 1010 wherein the wheel assembly componentidentification (ID) number is recorded. In the example depicted in FIG.10, the wheel assembly component ID is recorded as ABCD-1.Alternatively, the table 1000 may comprise a field 1020 wherein the typeof wheel assembly component which corresponds to the wheel assemblycomponent having the ID of field 1010 is recorded. In FIG. 10, the wheelassembly component with ID number ABCD-1 is recorded as a “bearingassembly”. The fields 1010 and/or 1020 may be recorded in table 1000during a provisioning process. Alternatively the fields 1010 and/or 1020may be recorded in table 1000 at the first instance that the database920 encounters the ID number in data received from the data managementmodule 910.

Table 1000 further comprises columns 1030, 1040 and 1050 which may bepopulated by data received from the data management module 910. Each rowin the table 1000 comprises the data from a read event, a read eventcomprising the receipt of a data transmission 132 from a tracking device110, at the tracking device reader 130, with redundant read eventfiltered by the data management module 910. Hence, the plurality of rowsin the table comprises a history of the wheel assembly component havingthe ID number recorded in field 1010. In one non-limiting embodiment,the column 1030 comprises the date of the read event. The date recordedin the column 1030 may comprise a date received from the tracking devicereader 130, for example in embodiments where the tracking device reader130 comprises a timing device. Alternatively, the date recorded in thecolumn 1030 may comprise a date and/or time added to the data at thedata management module 910, for example a date and/or time that the datawas received at the data management module 910. In yet anotheralternative embodiment, the date and/or time may comprise a date and/ortime added to the data by the database 920, for example a date and/ortime that the data was received at the database 920. In theseembodiments, the database 920 further comprises a timing device.

The column 1040 may comprise the geographic location of the trackingdevice reader 130, where the read event occurred. The geographiclocation recorded at column 1040 may be added to the data received atthe tracking device reader 130, for example in embodiments where thelocation of the tracking device reader 130 is stored in the memorymodule 540. Alternatively, the geographic location recorded at column1040 may be added to the data received by the tracking device reader 130from data received from the optional data input device 145, for examplein embodiments where the user input of the data input device 145comprises a location of the tracking device reader 130. Alternatively,the location of the tracking device reader 130 may be stored in thememory module 620 of the data input device 145, and added to the userinput prior to the transmission of data to the to the tracking devicereader 130.

In embodiments where the data returned from the tracking device reader130 does not comprise the geographic location of the tracking devicereader 130, but comprises an identification number of the trackingdevice reader 130, the geographic location of the tracking device reader130 may be retrieved by the database 920, from another table withindatabase 920, or another database accessible by the computing entity140.

A non-limiting example of a table 1100 comprising the identificationnumber of the tracking device reader 130, recorded along with thegeographic location of the tracking device reader 130, is depicted inFIG. 11. Table 1100 comprises at least one row, the at least one rowcomprising data related to the tracking device reader 130. Inembodiments of the systems depicted in FIGS. 1 and 3, which furthercomprise a plurality of tracking device readers 130, each at a differentgeographic location, each row in the table 1100 comprises data relatedto each of the plurality of tracking device readers 130, in a one-to-onerelationship.

Table 1100 may comprise a column 1110 comprising the tracking devicereader identification (ID) number. In a non-limiting example depicted inFIG. 11, the tracking device reader ID number recorded in the first rowcomprises TD-1. Table 1100 further comprises a column 1120, comprisingthe geographic location of the tracking device reader 130. Column 1120may contain as much data as necessary to uniquely identify the locationof the tracking device reader 130. In a non-limiting alternativeembodiment the table 1100 may further comprise a column 1130 comprisingan optional comment field, for recording additional informationassociated with the tracking device reader 130. In the non-limitingexample depicted in the first row of Table 1100, at column 1120, thelocation of the tracking device reader 130 with ID number TD-1 isrecorded as “Factory Floor”, indicating that it is located on the floorof a factory where wheel assembly components are manufactured. At column1130, the tracking device reader 130 with ID number TD-1 is identifiedas an “Initiation Point”, indicating that it is the first trackingdevice reader encountered by a tracking device 110 attached to a wheelassembly component after the wheel assembly component is manufactured.

In the non-limiting example depicted in the third row of Table 1100, atcolumn 1120, the location of the tracking device reader 130 with IDnumber TD-3 is recorded as “Yonge/Bloor Train Crossing, Toronto”,indicating that it is located at a train crossing near the intersectionof Yonge Street and Bloor Street in Toronto. At column 1130, thetracking device reader 130 with ID number TD-3 is identified as a “FixedLocation Device”.

However, in other embodiments, only the location of the tracking devicereader 130 may be recorded. In these embodiments, as illustrated in thefourth row of Table 11, a field in the column 1120 may be left blank.

In other embodiments, the column 1130 may also comprise data about thelocation of the tracking device 130. In the non-limiting exampledepicted in the fifth row of Table 1100, at column 1120, the location ofthe tracking device reader 130 with ID number TD-4 is recorded as“Chatham Ave, Toronto”, indicating that it is located adjacent to astretch of railway track near Chatham Avenue in Toronto. At column 1130,the tracking device reader 130 with ID number TD-5 is identified as a“Known Area of Problem Track”, indicating that there are known problemswith the railway track to which the tracking device reader with IDnumber TD-5 is adjacent.

In an alternative embodiment the Table 1100 may further comprise column1140, which comprises an indicator of whether a data input device 1140is connected to the tracking device reader 130. In the example depictedin FIG. 11, “Yes” indicates the presence of a data input device 1140 and“No” indicates that a data input device 1140 is not present.

The various columns of Table 1100 may be populated in a provisioningstep.

Returning to FIG. 10, the column 1050 of Table 1000 may comprise datadescribing an event associated with the read event. In one embodiment,the user input to the data input device 145 may comprise the dataassociated with the read event. In another embodiment, the data incolumn 1040 may comprise data from the sensor 430 of the tracking device110, or the sensor apparatus 1210. In the example depicted in the secondrow of FIG. 10, the event is identified as a “Shock Event”. In thisexample, the sensor 430 on tracking device 110 comprises a shock sensorand the data in column 1050 of row 2 is indicative that the shock sensorhas sensed a sudden change in acceleration to the tracking device 110.

In yet another embodiment, a given row may have an empty entry in theevent column 1050, as illustrated in the third row of Table 1000,indicating that there is no additional data associated with the readevent. In some embodiments, this may indicate that the tracking device110 has simply passed a certain location, as recorded in thecorresponding column 1040.

However, in alternative embodiments, the data populating the column 1050may also be referenced to a field in another Table within the database920. As illustrated in the fourth row of the Table 1000, the datapopulating the column 1050 has been populated with data from the column1130 of Table 1100, and comprises the data associated with thegeographic location of the tracking device reader 130 located at the“Chatham Ave Train Tracks”. Hence, at column 1050 it is recorded thatthe tracking device 110 has traversed a “Known Area of Problem Track”.

Table 1000 may further comprise a column 1060 which comprises datadedicated to a sensor 430 on the tracking device 110. Alternatively, inembodiments which comprise the sensor apparatus 1210, as depicted inFIG. 12, the column 1060 may further comprise data associated with thesensor apparatus 1210. In a non-limiting example depicted in FIG. 10,the column 1060 comprises data indicating “Temperature Events”associated with the temperature sensor 430 or the temperature sensordevice 1210, a temperature event comprising a temperature sensormeasuring the temperature of the wheel assembly component rising above athreshold value. In the embodiment depicted in FIG. 10, some of the dataof the column 1060 comprise the word “No”, indicating the absence of atemperature event, while others comprise the word “Yes”, indicating thepresence of a temperature event. As discussed previously, in embodimentswhere the wheel component assembly comprises the bearing assembly 160,the temperature of the bearing assembly 160 rising above a thresholdvalue may indicate that a bearing mechanism in the bearing assembly 160is worn out and requires machining. Within these embodiments, the numberof times that the temperature of the bearing assembly 160 rose above athreshold temperature may also indicate that the bearing mechanism inthe bearing assembly 160 is worn out and requires machining. Stillwithin these embodiments, the maximum measured temperature of thebearing assembly 160 may also indicate that the bearing mechanism in thebearing assembly 160 is worn out and requires machining.

Turning now to FIG. 13, database 920 may also comprise a table 1300, fortracking the distance traversed by a wheel assembly component. The table1300 is substantially similar to the table 1000, with like data fieldsrepresented by like numbers. The table 1300 differs from table 1000 inthat it includes a column 1310 for recording the cumulative distancetraversed by the wheel assembly component. In other embodiments, thedistance travelled by the wheel assembly component between trackingdevice readers 130 may be recorded at the column 1310. In thisembodiment, it is understood that a plurality of tracking device readers130 will be deployed generally adjacent to a plurality of expectedlocations of a wheel assembly component, and that the distance betweeneach of the plurality of tracking device readers 130 is known, such thatthe cumulative distance traversed by the wheel assembly component may betracked.

In some embodiments, the cumulative distance recorded at the column 1310may be calculated by the data management module 910. In otherembodiments, the cumulative distance may be recorded at the trackingdevice 110, based on data transmitted to the tracking device 110 fromthe plurality of tracking device readers 130. In these embodiments, thecumulative distance may be calculated by each of the tracking devicereaders 130 by retrieving the current recorded cumulative distance fromthe tracking device 110, calculating the cumulative distances based onthe current recorded distance and the location of the tracking devicereader 130. The cumulative distance may then be transmitted to thecomputing entity 140 for storage at the database 920, and transmitted tothe tracking device 110 for storage. In other embodiments, the totalcumulative distance may be stored primarily at the tracking device 110until it reaches a tracking device reader 130 located at a destination,the tracking device reader 130 located at the destination configured toretrieve the cumulative distance travelled by the tracking device 110.

Returning now to the computing entity 140 depicted in FIG. 9, the datamanagement module 910 may be further configured to determine if a wheelassembly component is due for maintenance. For example, the datamanagement module 910 may be configured to periodically examine therecords of database 920 and determine if any of the wheel assemblycomponents having a record in the database are due for maintenance. If awheel assembly component is due for maintenance, the data managementmodule 920 may be configured to transmit a message to a user of thesystems of any of FIGS. 1, 3 and 12, for example via an e-mail, or analert sent to a user device such as a telephony device. Alternatively,the data management module 910 may instruct the communication module 930to transmit the message. In yet another embodiment, the data managementmodule 910 may instruct the database 920 to create yet another table ofidentification numbers of wheel assembly components which are due formaintenance, for later retrieval by a user. In yet another embodiment,the data management module 910 may transmit an indicator to the trackingdevice reader 130, the indicator comprising the identification number ofa wheel assembly component which is due for maintenance. In theseembodiments, the tracking device reader 130 may be further configured totransmit a message to a user of the systems of any of FIGS. 1, 3 and 12,as described above, if the identification number of the wheel assemblycomponent is encountered while retrieving data from the tracking device110.

In another embodiment, the data management module 910 may be configuredto consult the records of database 920 when data associated with a wheelassembly component arrives at the data management module 910. Thehistory of the wheel assembly component may be determined at this time.If a wheel assembly component is due for maintenance, the message may betransmitted to a user immediately, or the identification number of thewheel assembly component may be stored in the appropriate table ofdatabase 920.

Criteria which may be used by the data management module 910 fordetermining if a wheel assembly component is due for maintenanceinclude:

-   -   the time period that a wheel assembly component has been in        service exceeding a threshold time period;    -   the distance that a wheel assembly component has travelled        exceeding a threshold distance;    -   the occurrence of one or more events as detected by the sensor        430 or the sensor apparatus 1210, as described previously,        including but not limited to exceeding a threshold, the number        of times a threshold is exceeded, the length of time a threshold        is exceeded, or a combination thereof;    -   the occurrence of a temperature event as detected by the        temperature sensor device 1210.

Other criteria, which may be used for determining if a wheel assemblycomponent is due for maintenance, may occur to one of skill in the art,and are within the scope of the present invention.

Non-limiting embodiments for attachment of the tracking device 110 to acomponent of the wheel assembly 120 are now considered. In general, manywheel assembly components are rotatable objects, and hence the trackingdevice 110 is configured for attachment to a rotatable object. Further,to minimize variations in the rotational momentum of the rotatable wheelassembly component while rotating, many wheel assembly components aresymmetric about an axis of rotation. Hence, as the wheel assemblycomponents are rotatable objects, the tracking device 110 may beconfigured to maintain the balanced rotation of the wheel assemblycomponent when the wheel assembly component is rotating.

An exploded view of one example of a wheel assembly component isdepicted in FIG. 14, depicting detail of the bearing assembly 160, andfurther depicting the tracking device 110 in a position of attachment onthe bearing assembly 160.

In this non-limiting embodiment, the bearing assembly 160 comprises abearing assembly body 1410. The bearing assembly body 1410 generallycomprises a plurality of components including the vehicle frame portion,the wheel portion and the bearing portion discussed previously. In onenon-limiting example, the bearing assembly body 1410 is cylindrical innature with a cylindrical axis of symmetry 1415, which is aligned withthe axis of rotation of the bearing assembly.

The bearing assembly body 1410 further comprises an end configured forattachment to a wheel, such as the wheel 220 discussed above, wherebythe axis of symmetry 1415 will be in alignment with the axis of rotationof the wheel, and an opposite end comprising a face 1420. Further, theface 1420 shares the axis of symmetry 1415 of the bearing assembly body1410.

The bearing assembly 160 further comprises a plate 1430, which isconfigured for attachment to the face 1420. In the depicted non-limitingembodiment, the plate 1430 exhibits triangular symmetry about a centralaxis 1435, however in other non-limiting embodiments, the plate 1430 maynot be triangular. In yet other non-limiting embodiments, the plate 1430may not be symmetric. Other shapes of the plate 1430 may occur to one ofskill in the art and are within the scope of the present invention.

The plate 1430 is configured for attachment to the face 1420 via afastening mechanism. In the embodiment depicted in FIG. 14, thefastening mechanism comprises at least one fastener 1440, and at leastone receptacle 1450 in the face 1420 for receiving the at least onefastener 1440. The plate 1430 comprises at least one hole 1460 for eachfastener 1440/receptable 1450 pair, the at least one hole 1460 arrangedin a pattern complementary to the pattern of the at least one receptacle1450, such that the at least one fastener 1440 may be passed through theat least one hole 1460 and received by the at least one receptacle 1450.In one non-limiting embodiment, the at least one fastener comprises 1440a bolt, and the at least one receptacle 1450 comprises a threaded bore.

In general, the fastening mechanism will be configured for attaching theplate 1430 to the face 1420 such that the central axis 1435 of the plate1430 is aligned with the axis of symmetry 1415 of the bearing assemblybody 1410. In some embodiments, the plate 1430 further comprises acentral opening 1470. In some embodiments, the central opening 1470 isrotationally symmetric about the central axis 1435 of the plate 1430. Insome non-limiting embodiments, the central opening 1470 may be circular.In other non-limiting embodiments, the opening 1470 may be triangular orsquare. However other shapes of the opening 1470 may occur to one ofskill in the art and are within the scope of the present invention.

In some embodiments, the at least one fastener 1440 may further serve tolock together bearing assembly components that comprise the bearingassembly body 1410. Hence in embodiments where the at least one fastener1440 comprises a bolt, the screw or bolt may be attached with a givenamount of torque to ensure that the bearing assembly components remainlocked together. Within these embodiments, the plate 1430 comprises alocking plate for ensuring that the at least one fastener 1440 maintainsthe given amount of torque: i.e. the at least one fastener 1440 does notcome loose. In this embodiment, the locking plate may comprise abearing-side surface configured for abutment to the face 1420, and anoppositely located locking surface, comprising a washer mechanism formaintaining the given torque of the bolt when it is in an attachedposition. In one non-limiting embodiment, the washer mechanism maycomprise a raised portion of the plate 1430, compressible by a head ofthe bolt.

Turning now to an embodiment of the tracking device 110, which isdepicted in a position of attachment in FIG. 14, with reference to FIGS.15A, 15B, and 15C, the tracking device 110 comprises a body 1510 havinga central axis 1515, the body 1510 being rotationally symmetric aboutthe central axis 1515. The tracking device 110 further comprises anattachment section connected to the body 1510. In this example, theattachment section comprises at least one attachment member connected tothe body. In some embodiments, the attachment member comprises at leasttwo arms, configured symmetrically about the central axis 1515. In thedepicted non-limiting embodiment, the at least one attachment membercomprises three arms 1520 a, 1520 b and 1520 c, configured symmetricallyabout the central axis 1515, with an angle of approximately 120° betweeneach arm. However, in other embodiments, the attachment member maycomprise a different number of arms, configured symmetrically about thecentral axis 1515. A symmetrical configuration of the arms may assistwith maintaining the balanced rotation of the wheel assembly componentwhen the tracking device 110 is attached to the wheel assemblycomponent, and the wheel assembly component is rotating. However, insome embodiments, a non-symmetrical configuration of the arms may alsoassist with maintaining the balanced rotation of the wheel assemblycomponent when the tracking device 110 is attached to the wheel assemblycomponent, and the wheel assembly component is rotating. In theseembodiments, a counterweight may be present on the body 1510 tocompensate for any shift in the centre of mass of the tracking device110 that may occur due to a non-symmetrical configuration of the arms.

The body 1510 further comprises a tracking portion 1530. In embodimentswhere the tracking device 110 comprises an electronic tracking device,the tracking portion 1530 comprises the elements depicted in FIG. 4,described previously. Within these embodiments, the tracking portion1530 may be encased in the body 1510, while in other embodiments thetracking portion 1510 may be located on the body 1510. In embodimentswhere the tracking device 110 comprises an optical tracking device, thetracking portion 1530 holds the graphical representation of the dataassociated with a wheel assembly component, described previously. Inthese embodiments, the tracking portion 1530 may be encased in the body1510, the body 1510 being optically transparent such that the trackingportion 1530 is readable by the tracking device reader 130, when thetracking device 110 is in a position of attachment to the wheel assemblycomponent. For example, in embodiments where the tracking portion 1530holds a barcode, and the barcode is encased by the body 1510, thebarcode must be optically visible to the tracking device reader 130through the body 1510. However, in other embodiments, the trackingportion 1530 may be located on the body 1510, at a position where thetracking portion 1530 is visible to the tracking device reader 130 in aposition of attachment to the wheel assembly component.

In some embodiments, the body 1510 is elongate and comprises an abutmentend 1540 and a distal end 1545. In some embodiments, the at least oneattachment member may be flush to the abutment end 1540 and/or connectedto the abutment end 1540. However, in other embodiments, the at leastone attachment member may be connected to the abutment end 1540, thedistal end 1545, or between the distal end 1545 and the abutment end1540. In these embodiments, the at least one attachment member may bebendable, as discussed below, such that when the tracking device 110 isattached to the wheel assembly component, the at least one attachmentmember may be clamped between the plate 1430 and the face 1420, asdiscussed below. In other embodimentsm the face 1420 may comprise arecessed area, configured to receive the abutment end 1540; hence, theat least one attachment member may be connected to the location on thebody 1510 which allows the at least one attachment member to lie acrossthe face 1420 when the body 1510 is inserted into the recessed area.

However, in general, the abutment end 1540 may be configured forabutment to the wheel assembly component, for example to the face 1420of the bearing assembly 160. In the embodiments depicted in FIGS. 14 and15A, 15B and 15C, the abutment end 1540 is planar in nature, forabutment against the face 1420.

In some instances, the wheel assembly component may be comprised ofmaterials which may interfere with the contactless reading of thetracking portion 1530, by the tracking device reader 110, when thetracking device 110 is attached to the wheel assembly component. Inthese embodiments, the tracking portion 1530 may be located closer tothe distal end 1545 than the abutment end 1540. For example, in someembodiments, the wheel assembly component is comprised of a metal, whichmay generally interfere with RF signals received and/or transmitted bysome types of electronic tracking devices, such as certain RFID devices.Hence, in these embodiments, locating the tracking portion 1530 closerto the distal end 1545 of the elongated body 1510 displaces the trackingportion 1530 from the abutment end 1540, such that when the abutment end1540 is in contact with a metallic wheel assembly component, electronicinterference is reduced.

However, in other instances, the wheel assembly component may becomprised of materials which may not interfere with the contactlessreading of the tracking portion 1530, by the tracking device reader 110,when the tracking device 110 is attached to the wheel assemblycomponent. In these embodiments, the tracking portion 1530 may belocated near the distal end 1545, near the abutment end 1540 or inbetween. Further, in these embodiments, the body 1510 may not beelongate. FIG. 15D depicts another non-limiting embodiment of thetracking device 110, similar to the tracking device depicted in FIG.15C, with like components represented by like numbers. In thisembodiment, the body 1510 may not be elongate, and the tracking portion1530 will be located adjacent to the wheel assembly component when thetracking device 110 is attached to the wheel assembly component.

In embodiments where the plate 1430 comprises a central opening 1470,the cross-section of the body 1510 may be configured to be less than thecross section of the central opening 1470. In embodiments where the body1510 is cylindrical, and the central opening 1470 is circular, thediameter of the body 1510 may be configured to be less than the diameterof the central opening 1470. Hence, in embodiments where the body 1510is elongate, the body 1510 may be configured to extend through thecentral opening 1470, when the tracking device 110 is attached to thewheel assembly component. An example of this configuration is depictedin FIG. 14, whereby the cylindrical body 1510 of the tracking device 110will extend through the central opening 1470 when the plate 1430 isattached to the face 1420.

In some embodiments, the body 1510 may be further comprised of a shell,the shell made of a plastic, including but not limited topolypropylenes, epoxies, and resins. Other types of plastics may includeplastics which may be formed into shapes using an overmolded orinjection molding process. In other embodiments, the body 1510 may becomprised of a metal. Other materials that may comprise the body willoccur to those of skill in the art and are within the scope of thepresent invention.

Returning now to the at least one attachment member, at least a portionof each of the at least one attachment member is configured for clampedretention between the face 1420 and the plate 1430, with sufficientforce to prevent the tracking device 110 from being released when thetracking device 110 is in an attached position, and while the rotatableobject to which it is attached is rotating. Within the embodimentdepicted in FIGS. 14, 15A, 15B, and 15C, arms 1520 a, 1520 b and 1520 cwhich comprise the at least one attachment member, are configured to beclamped between the face 1420 and the plate 1430 when the plate 1430 isattached to the face 1420.

With reference to FIG. 15E, depicting detail of arm 1520 a, in generalthe arms 1520 a, 1520 b and 1520 c will comprise a given length, L, agiven width, W, and a given thickness, T, the given thickness Tseparating a first surface, S1 and a second surface, S2, wherein thefirst surface S1 and the second surface S2 are substantially parallel.The first surface S1 and the second surface S2 are configured forcontact with the plate 1430 and the face 1420 respectively, when thetracking device 110 is in an attached position.

The given length L corresponds to the distance the arms 1520 a, 1520 band 1520 c extend from the body 1510.

The dimensions L, W and T of each of the arms 1520 a, 1520 b and 1520 care configured to allow the plate 1430 to be attached to the face 1420,without comprising the given torque of the fastening mechanism, when thetracking device 110 is in an attached position. For example, when thefastening mechanism comprises at least one bolt, at least one hole 1460,and at least one bolt hole in the face 1420, the at least one bolt isgenerally tightened to the given amount of torque, as discussed above.When the tracking device 110 is in the attached position, the presenceof the arms 1520 a, 1520 b and 1520 c between the plate 1430 and theface 1420 should not cause the bolts to loosen.

Furthermore, in this embodiment, when the tracking device 110 is in theattached position, the plate 1430 may not actually be in contact withthe face 1420, with the entire clamping force between the plate 1430 andthe face 1420 being borne by the first surface and the second surface.Hence first surface S1 and second surface S2 are substantially parallel,and the clamping force is evenly distributed along the first surface andthe second surface.

When the tracking device 110 is in the attached position, at least aportion of each of the arms 1520 a, 1520 b and 1520 c may be clampedbetween the plate 1430 and the face 1420. In some embodiments, each ofthe arms 1520 a, 1520 b and 1520 c is configured to extend from the body1510 to a point between an edge of the central opening 1470 of the plate1430 and an outer edge of the plate 1430, when the tracking device 110is in the attached position. In other embodiments, each of the arms 1520a, 1520 b and 1520 c is configured to extend from the body 1510 to anouter edge of the plate 1430, when the tracking device 110 is in theattached position.

In yet other embodiments, each of the arms 1520 a, 1520 b and 1520 c isconfigured to extend from the body 1510 to beyond the outer edge of theplate 1430, when the tracking device 110 is in the attached position. Insome of these embodiments, at least a portion of each of the arms 1520a, 1520 b and 1520 c configured to extend beyond an outer edge of theplate, may be bendable. In these embodiments, the given thickness T maybe substantially less than the given length L. In these embodiments, thebendable portion of each of the arms 1520 a, 1520 b and 1520 c may beused to facilitate the securing of the tracking device 110 to the plate1430, prior to attaching the plate 1430 to the face 1420. In otherwords, the tracking device 110 is secured to the plate 1430 as each ofthe arms 1520 a, 1520 b and 1520 c are wrapped around an edge of theplate 1430. This situation is illustrated in FIGS. 16A, 16B, 17A and17B, which together depict a method of securing the tracking device 110to the plate 1430, prior to attaching the plate 1430 to the face 1420.

FIG. 16A depicts a perspective view of an embodiment of the inventionwherein a portion 1610 of the given length L is configured to extendbeyond the outer edge of the plate 1430. FIG. 16A further depicts thebody 1510 and arms 1520 a, 1520 b, and 1520 c of the tracking device110, in a position wherein the body 1410 has been inserted through thecentral opening 1470 of the plate 1430. In this position, the firstsurface S2 of each of the arms 1520 a, 1520 b, and 1520 c are adjacentto the bearing-side surface of the plate 1430.

FIG. 16B depicts a side view of the embodiment depicted in FIG. 16A whenviewed from the bearing-side surface of the plate 1430. FIG. 16B furtherdepicts the relative position of the surface S2 of the arm 1520 b to thebearing-side surface of the plate 1430.

FIG. 17A depicts a perspective view of an embodiment of the invention,similar to the embodiment depicted in FIG. 16A, wherein the portion 1610is bent around an edge of the plate 1430. In this position, the firstsurface S1 is now in contact with the side opposite the bearing-sidesurface of the plate 1430, and the second surface S2 faces away from theplate 1430. FIG. 17B depicts a side view of the embodiment depicted inFIG. 17A when viewed from the bearing-side surface of the plate 1430.From this perspective, the portion 1610 is in the bent position andhence not visible.

In the embodiment depicted in FIGS. 17A and 17B, when the portion 1610is in the bent position, the arms 1520 a, 1520 b, and 1520 cfrictionally retain the tracking device 110 to the plate 1430. The plate1430 may then be attached to the face 1420 without regard for holdingthe tracking device 110 between the plate 1420 and the face 1430.

FIG. 18A depicts a perspective view of an alternative embodiment of theplate 1430, wherein the plate 1430 is lacking the central opening 1470.An end of the body 1410 is configured for abutment against the surfaceof the plate 1430 opposite the bearing side surface, in an attachedposition. FIG. 18A further depicts the relative position of surface S1with respect to the plate 1430. FIG. 18B depicts a side view of theembodiment depicted in FIG. 18A when viewed from the bearing-sidesurface of the plate 1430, and further depicts the relative position ofsurface S2 with respect to the plate 1430.

FIG. 19 depicts a side view of an embodiment of the invention whenviewed from the bearing-side surface of the plate 1430, similar to theembodiment depicted in FIG. 17B, wherein the portion 1610 is bent aroundan edge of the plate 1430. In this position, the second surface S2 is incontact with the bearing-side surface of the plate 1430, and the firstsurface Si faces outwards from the plate 1430. In this embodiment, theportion 1610 of the arms 1520 a, 1520 b, and 1520 c secure the trackingdevice 110 to the plate 1430. The plate 1430 may then be attached to theface 1420, and the portion 1610 is clamped between the plate 1430 andthe face 1420.

FIG. 20 depicts a perspective view of yet another non-limitingembodiment of the at least one attachment member, comprising a lip 2010connected to the body 1510. The lip 2010 comprises a rotationallysymmetric circumferential lip extending from the body 1510,substantially perpendicular to the central axis 1515. In thisembodiment, the lip 2010 is configured for clamped retention between theplate 1430 and the face 1420, when the body 1510 extends through thecentral opening 1470 of the plate 1430. In yet further embodiments, thelip 2010 may not be completely circumferential and only portions of thedepicted lip 2010 may be present.

FIG. 21 depicts a side view of yet another non-limiting embodiment ofthe attachment member, comprising a web portion 2110 connected to thebody 1510, the web portion 2110 configured for clamped retention forclamped retention between the plate 1430 and the face 1420 when the body1510 extends through the central opening 1470 of the plate 1430. The webportion 2110 comprises at least one arm portion 2120, connected to atleast one auxiliary retention member 2130. While the web portion 2110depicted in FIG. 21 comprises two arm portions 2120 and one auxiliaryretention member 2130, other arrangements of arm portions 2120 andauxiliary retention members 2130 will occur to those of skill in the artand are within the scope of the present invention.

FIG. 22A depicts a perspective view of yet another non-limitingembodiment of the attachment member. The bearing assembly componentsdepicted in FIG. 22A are similar to the bearing assembly componentsdepicted in FIG. 14, with like components represented by like numbers.In this embodiment, the at least one attachment member comprises atracking portion attachment plate 2210, configure for clamped retentionbetween the plate 1430 and the face 1420. The tracking portionattachment plate 2210 may be rotationally symmetric about a central axis2215. The tracking portion attachment plate 2210 further comprises atleast one fastener receiving hole 2220, arranged in a patterncomplementary to the pattern of the at least one receptacle 1450. Hence,the at least one fastener 1440 may pass through both the at least onehole 1460 in the plate 1430, and the at least one fastener receivinghole 2220 in the tracking portion attachment plate 2210, for fasteningthe plate 1430 and the tracking portion attachment plate 2210 to theface 1420.

The tracking portion attachment plate 2210 further comprises at leastone tracking portion fastener receptacle 2230, for attaching the body1510 of the tracking device 110 as depicted in FIGS. 15A, 15B and 15C,to the tracking portion attachment plate 2210. FIG. 22A further depictsvarious possible locations of the at least one tracking portion fastenerreceptacle 2230. In embodiments which comprise a single tracking portionfastener receptacle 2230, the single tracking portion fastenerreceptacle 2230 may be located at the centre of the tracking portionattachment plate 2210, along the central axis 2215. In otherembodiments, the at least one tracking portion fastener receptacle 2230may be located adjacent to an edge of the tracking portion attachmentplate 2210 and configured to be accessible when the tracking portionattachment plate 2210 is clamped between the plate 1430 and the face1420. Further, in embodiments where the tracking portion attachmentplate 2210 comprises a plurality of tracking portion fastenerreceptacles 2230, the locations of the plurality of tracking portionfastener receptacles 2230 may be configured with rotational symmetry.However, in other embodiments, the locations of the plurality oftracking portion fastener receptacles 2230 may not be configured withrotational symmetry, as long as the balanced rotation of wheel assemblyis maintained, for example via the use of counterweights.

FIG. 22B depicts a cross-section through line BB of FIG. 22A, showingone embodiment of an attachment mechanism for attaching the body 1510 tothe tracking portion attachment plate 2210. Within this embodiment, athreaded shaft 2240 extends from the body 1510, and the at least onetracking portion fastener receptacle 2230 comprises a threaded bore2235, for receiving the threaded shaft 2240. The threaded shaft 2240 maybe screwed into the threaded shaft 2235, attaching the body 1510 to thetracking portion attachment plate 2210.

FIG. 22B also depicts a counterweight 2250 for countering the weight ofthe body 1510, in embodiments where the body 1510 is attached to thetracking portion attachment plate 2210 at a tracking portion fastenerreceptacle 2230 that is not located along the central axis 2215. In thisembodiment the counterweight 2250 may be attached to the trackingportion attachment plate 2210 at a location which counters the weight ofthe body 1510, so as to maintain the balanced rotation of the wheelassembly component, when the wheel assembly component is rotating, forexample, at another tracking portion fastener receptacle 2230. In thedepicted embodiment, the counterweight 2250 is attachable to thetracking portion attachment plate 2210 via an attachment mechanismsimilar to the attachment mechanism described above in relation to thebody 1510. In other embodiments, the counterweight 2250 may beattachable to the tracking portion attachment plate 2210 via a differentattachment mechanism. In some embodiments, the counterweight 2250 may bepermanently attached to the tracking portion attachment plate 2210, orcomprise a part of plate 2210.

In some embodiments (not depicted), the attachment member depicted inFIG. 22A may further comprise areas surrounding the at least onetracking portion fastener receptacle 2230 that are raised, to facilitatethe displacement of the tracking portion 1530 from the wheel assemblycomponent, as described earlier.

A method of refurbishing the bearing assembly 160 will now be describedwith reference to FIG. 23. In order to assist in the explanation of themethod, it will be assumed that the method of FIG. 23 is operated usingany of the embodiments of the tracking device 110 depicted in FIGS.14-22B, or any embodiments of the plate 1430 depicted in FIG. 14 or 18.It should be understood that the steps in the method of FIG. 23 need notbe performed in the sequence shown. Further, it is to be understood thatthe tracking devices of FIGS. 14-22 and/or the plates of FIGS. 14 and19, and/or the method of FIG. 23 can be varied, and need not work asdiscussed herein in conjunction with each other, and that suchvariations are within the scope of the present invention.

At step 2510, some embodiments comprise disassembling the bearingassembly 160. In one non-limiting embodiment, the bearing assembly 160comprises a plurality of components, which includes the bearing assemblybody 1410, and the plate 1430. The bearing assembly 160 furthercomprises components which rotate relative to one another, for examplethe vehicle frame portion and the wheel portion, described previously.To facilitate the rotation between them, the vehicle frame portion andthe wheel portion may be in contact via a bearing portion as known toone of skill in the art. In some embodiments, disassembling of thebearing assembly may be triggered by the bearing portion requiringmaintenance, as indicated by a bearing assembly 160 that heats up whilein use, as discussed previously. In any event, disassembling the bearingassembly 160 comprises separating the various components by looseningand/or removing fastening devices, etc.

At step 2520, some embodiments may comprise machining at least onecomponent of the bearing assembly 160. In one non-limiting embodiment,machining at least one component of the bearing assembly 160 comprisesmachining the bearing portion to remove rough spots. However, in otherembodiments, machining at least one component of the bearing assembly160 may comprise machining another component to facilitate the rotationof the wheel portion relative to the vehicle frame portion.

At step 2525, some embodiments may comprise replacing at least onecomponent of the bearing assembly. In one non-limiting embodiment,replacing at least one component of the bearing assembly 160 comprisesreplacing the bearing portion, if its condition has degraded to thepoint where it cannot be fixed with machining. However, in otherembodiments, replacing at least one component of the bearing assembly160 may comprise replacing another component to facilitate the rotationof the wheel portion relative to the vehicle frame portion.

At step 2530, some embodiments comprise reassembling the bearingassembly 160. In some embodiments, reassembling the bearing assembly 160comprises reassembling the vehicle portion, the wheel portion and thebearing portion. In some non-limiting embodiments, reassembling thebearing assembly 160 further comprises clamping the tracking device 110between a plurality of components of the bearing assembly 160. In someembodiments, the clamping of the tracking device 110 between a pluralityof components of the bearing assembly 160 comprises clamping thetracking device 110 between the plate 1430 and the face 1420, asdescribed previously with reference to FIGS. 14 to 15D. Other optionsdescribed previously with reference to FIGS. 16 to 22B may also beutilized.

Those skilled in the art will appreciate that certain functionality ofthe computing entity 140, the reader 130, the tracking device 110 and/orother elements of the infrastructure described herein may be implementedas pre-programmed hardware or firmware elements (e.g., applicationspecific integrated circuits (ASICs), electrically erasable programmableread-only memories (EEPROMs), etc.), or other related components. Inother embodiments, certain portions of the computing entity 140, thereader 130, the tracking device 110 and/or other elements may beimplemented as an arithmetic and logic unit (ALU) having access to acode memory (not shown) which stores program instructions for theoperation of the ALU. The program instructions could be stored on amedium which is fixed, tangible and readable directly by the computingentity 140, the reader 130, the tracking device 110 and/or otherelements, (e.g., removable diskette, CD-ROM, ROM, fixed disk, USBdrive), or the program instructions could be stored remotely buttransmittable to the computing entity 140, the reader 130, the trackingdevice 110 and/or other elements via a modem or other interface device.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible for implementingthe present invention, and that the above implementations and examplesare only illustrations of one or more embodiments of the presentinvention. The scope of the invention, therefore, is only to be limitedby the claims appended hereto.

1. A method of determining whether to effect maintenance of a vehiclecomponent comprising: transmitting an RFID read signal to an RFID deviceassociated with at least one component of a vehicle; receiving at leastone RFID response signal from the RFID device, the at least one RFIDresponse signal comprising an identifier associated with the at leastone component and a sensed value of a parameter associated with the atleast one component; and processing the sensed value to determinewhether to effect maintenance of the at least one component.
 2. Themethod of claim 1, wherein the at least one RFID response signalcomprises an RFID response signal comprising both the identifier and thesensed value.
 3. The method of claim 1, wherein the at least one RFIDresponse signal comprises at least a first RFID response signalcomprising the identifier and a second RFID response signal comprisingthe sensed value.
 4. The method of claim 1, wherein the sensed value ofa parameter comprises at least one of a temperature event, a vibrationevent, a shock event, a gyroscopic event, a pressure event, a torqueevent and a tamper event.
 5. The method of claim 1, wherein the sensedvalue of a parameter comprises at least one output from a sensor coupledto the RFID device.
 6. The method of claim 5, wherein the sensor isincorporated within the RFID device.
 7. The method of claim 5, whereinthe at least one output from the sensor comprises an indication of atemperature event associated with the at least one component.
 8. Themethod of claim 7, wherein the indication of a temperature eventcomprises at least one of a temperature associated with the at least onecomponent, a maximum temperature associated with the at least onecomponent, a minimum temperature associated with the at least onecomponent, an indication that a temperature associated with the at leastone component exceeded a threshold temperature, an indication of anumber of occurrences that a temperature associated with the at leastone component exceeded a threshold temperature and an indication of alength of time that a temperature associated with the at least onecomponent exceeded a threshold temperature.
 9. The method of claim 7,wherein the processing the sensed value comprises comparing theindication of a temperature event with an acceptable temperature eventlimit for the at least one component and determining to effectmaintenance of the at least one component if the indication of thetemperature event exceeds the acceptable temperature event limit. 10.The method of claim 5, wherein the at least one output from the sensorcomprises an indication of a vibration event associated with the atleast one component.
 11. The method of claim 10, wherein the indicationof a vibration event comprises at least one of a vibration associatedwith the at least one component, a maximum vibration associated with theat least one component, an indication that a vibration associated withthe at least one component exceeded a threshold vibration, an indicationof a number of occurrences that a vibration associated with the at leastone component exceeded a threshold vibration and an indication of alength of time that a vibration associated with the at least onecomponent exceeded a threshold vibration.
 12. The method of claim 10,wherein the processing the sensed value comprises comparing theindication of a vibration event with an acceptable vibration event limitfor the at least one component and determining to effect maintenance ofthe at least one component if the indication of the vibration eventexceeds the acceptable vibration event limit.
 13. The method of claim 5,wherein the at least one output from the sensor comprises an indicationof a shock event associated with the at least one component.
 14. Themethod of claim 13, wherein the indication of a shock event comprises anindication of a change of acceleration of the at least one component.15. The method of claim 5, wherein the at least one output from thesensor comprises an indication of a gyroscopic event associated with theat least one component.
 16. The method of claim 15, wherein theindication of a gyroscopic event comprises at least one of an indicationof a change in orientation of the at least one component, an indicationof a number of occurrences of change of orientation of the at least onecomponent and an indication of a length of time that change oforientation occurred for the at least one component.
 17. The method ofclaim 15, wherein the processing the sensed value comprises comparingthe indication of a gyroscopic event with an acceptable gyroscopic eventlimit for the at least one component and determining to effectmaintenance of the at least one component if the indication of thegyroscopic event exceeds the acceptable gyroscopic event limit.
 18. Themethod of claim 5, wherein the at least one output from the sensorcomprises an indication of a pressure event associated with the at leastone component.
 19. The method of claim 18, wherein the indication of apressure event comprises at least one of a pressure associated with theat least one component, a maximum pressure associated with the at leastone component, a minimum pressure associated with the at least onecomponent, an indication that a pressure associated with the at leastone component exceeded a threshold pressure, an indication of a numberof occurrences that a pressure associated with the at least onecomponent exceeded a threshold pressure and an indication of a length oftime that a pressure associated with the at least one component exceededa threshold pressure.
 20. The method of claim 18, wherein the processingthe sensed value comprises comparing the indication of a pressure eventwith an acceptable pressure event limit for the at least one componentand determining to effect maintenance of the at least one component ifthe indication of the pressure event exceeds the acceptable pressureevent limit.
 21. The method of claim 5, wherein the at least one outputfrom the sensor comprises an indication of a torque event associatedwith the at least one component.
 22. The method of claim 21, wherein theindication of a torque event comprises at least one of a torqueassociated with the at least one component, a maximum torque associatedwith the at least one component, a minimum torque associated with the atleast one component, an indication that a torque associated with the atleast one component exceeded a threshold torque, an indication of anumber of occurrences that a torque associated with the at least onecomponent exceeded a threshold torque and an indication of a length oftime that a torque associated with the at least one component exceeded athreshold torque.
 23. The method of claim 21, wherein the processing thesensed value comprises comparing the indication of a torque event withan acceptable torque event limit for the at least one component anddetermining to effect maintenance of the at least one component if theindication of the torque event exceeds the acceptable torque eventlimit.
 24. The method of claim 5, wherein the at least one output fromthe sensor comprises an indication of a tamper event associated with theat least one component.
 25. The method of claim 24, wherein theindication of a tamper event comprises an indication that at least oneof the tracking device and the at least one component have been tamperedwith.
 26. The method of claim 1 further comprising transmitting amaintenance indication to the RFID device if it is determined to effectmaintenance of the at least one component.
 27. A system comprising: anRFID device reader configured to: transmit an RFID read signal to anRFID device associated with at least one component of a vehicle; andreceive at least one RFID response signal from the RFID device, the atleast one RFID response signal comprising an identifier associated withthe at least one component and a sensed value of a parameter associatedwith the at least one component; and a computing entity configured to:process the sensed value to determine whether to effect maintenance ofthe at least one component.
 28. The system of claim 27, wherein the atleast one RFID response signal comprises an RFID response signalcomprising both the identifier and the sensed value.
 29. The system ofclaim 27, wherein the at least one RFID response signal comprises atleast a first RFID response signal comprising the identifier and asecond RFID response signal comprising the sensed value.
 30. The systemof claim 27, wherein the sensed value of a parameter comprises at leastone of a temperature event, a vibration event, a shock event, agyroscopic event, a pressure event, a torque event and a tamper event.31. The system of claim 27 further comprising the RFID device.
 32. Thesystem of claim 31 further comprising a sensor coupled to the RFIDdevice and configured to sense the sensed value of a parameterassociated with the at least one component, the sensed value of aparameter comprising at least one output from the sensor.
 33. The systemof claim 32, wherein the sensor is incorporated within the RFID device.34. The system of claim 32, wherein the at least one output from thesensor comprises at least one of a temperature event, a vibration event,a shock event, a gyroscopic event, a pressure event, a torque event anda tamper event.
 35. The system of claim 27, wherein the RFID devicereader and the computing entity are integrated within a single entity.36. The system of claim 27, wherein the RFID device reader and thecomputing entity are communicatively coupled via a network.
 37. Thesystem of claim 27, wherein the RFID device reader is further configuredto transmit a maintenance indication to the RFID device if it isdetermined to effect maintenance of the at least one component. 38.(canceled)
 39. (canceled)
 40. (canceled)
 41. (canceled)
 42. (canceled)43. (canceled)
 44. (canceled)
 45. (canceled)
 46. (canceled) 47.(canceled)
 48. (canceled)
 49. (canceled)
 50. (canceled)
 51. (canceled)52. (canceled)
 53. (canceled)
 54. (canceled)
 55. (canceled) 56.(canceled)
 57. (canceled)
 58. (canceled)
 59. (canceled)
 60. (canceled)61. (canceled)
 62. (canceled)
 63. (canceled)
 64. (canceled) 65.(canceled)
 66. (canceled)
 67. (canceled)
 68. (canceled)
 69. (canceled)70. A system comprising: a tracking device, coupled to at least onecomponent of a vehicle, configured to rotate with movement of thevehicle and to transmit an identifier; a tracking device readerconfigured to: receive a sensed value of a parameter associated with theat least one component; and identify the at least one componentassociated with the sensed value by receiving the identifier of thetracking device; and a computing entity configured to: process thesensed value to determine whether to effect maintenance of the at leastone component.
 71. The system of claim 70, wherein the tracking deviceis an RFID device and to identify the component, the tracking devicereader is configured to transmit an RFID read signal to the trackingdevice and to receive an RFID response signal from the tracking device,the RFID response signal comprising the identifier of the trackingdevice.
 72. The system of claim 70, wherein the tracking device readeris configured to receive the sensed value from the tracking device. 73.The system of claim 72, wherein the tracking device reader is configuredto receive the identifier of the tracking device and the sensed valuefrom the tracking device together.
 74. The system of claim 72, whereinthe sensed value of a parameter comprises at least one of a temperatureevent, a vibration event, a shock event, a gyroscopic event, a pressureevent, a torque event and a tamper event.
 75. The system of claim 72,wherein the tracking device is an RFID device and to receive the sensedvalue, the tracking device reader is configured to transmit an RFID readsignal to the tracking device and receive an RFID response signal fromthe tracking device, the RFID response signal comprising the sensedvalue.
 76. The system of claim 75, wherein the RFID response signalfurther comprises the identifier of the tracking device.
 77. The systemof claim 72, further comprising a sensor coupled to the tracking device,wherein the sensed value of a parameter comprises at least one outputfrom the sensor.
 78. The system of claim 77, wherein the at least oneoutput from the sensor comprises at least one of a temperature event, avibration event, a shock event, a gyroscopic event, a pressure event, atorque event and a tamper event.
 79. The system of claim 70, furthercomprising a sensor located adjacent to an expected location of the atleast one component, wherein the sensed value of a parameter comprisesat least one output from the sensor.
 80. The system of claim 79, whereinthe at least one output from the sensor comprises an indication of atemperature event associated with the at least one component.
 81. Thesystem of claim 70, wherein the tracking device reader and the computingentity are integrated within a single entity.
 82. The system of claim70, wherein the tracking device reader and the computing entity arecommunicatively coupled via a network.
 83. The system of claim 70,wherein the tracking device reader is further configured to transmit amaintenance indication to the tracking device if it is determined toeffect maintenance of the at least one component.
 84. (canceled) 85.(canceled)
 86. (canceled)
 87. (canceled)
 88. (canceled)
 89. (canceled)90. (canceled)
 91. (canceled)
 92. (canceled)
 93. (canceled) 94.(canceled)
 95. (canceled)
 96. (canceled)
 97. (canceled)
 98. (canceled)99. (canceled)
 100. (canceled)
 101. (canceled)
 102. (canceled) 103.(canceled)
 104. (canceled)